Repository navigation
[draft] Preserve underscores in custom schema name prefixes - #7287
Open
lennartkats-db wants to merge 6 commits into
Open
lennartkats-db wants to merge 6 commits into
lennartkats-db wants to merge 6 commits into
Conversation
Collaborator
✅ Integration test reportCommit: d8674d9
Top 9 slowest tests (at least 2 minutes):
|
Contributor
|
Commit: Regression test reportSelected 2 changed tests (limit=20, 0 not selected) 4 tests: regression=4 unreleased=0 coverage=0 failing=0
TestAccept/bundle/presets/name_prefix_existing_schema/DMS=: branch ✅ | main (8e70c8b) ❌ | latest (v1.26.0) ❌main (8e70c8b): latest (v1.26.0): TestAccept/bundle/presets/name_prefix_existing_schema/DMS=true: branch ✅ | main (8e70c8b) ❌ | latest (v1.26.0) ❌main (8e70c8b): latest (v1.26.0): TestAccept/bundle/presets/name_prefix_underscores/DMS=: branch ✅ | main (8e70c8b) ❌ | latest (v1.26.0) ❌main (8e70c8b): latest (v1.26.0): same output as main (8e70c8b) TestAccept/bundle/presets/name_prefix_underscores/DMS=true: branch ✅ | main (8e70c8b) ❌ | latest (v1.26.0) ❌main (8e70c8b): latest (v1.26.0): |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
Preserve literal trailing and repeated underscores from custom
presets.name_prefixvalues in schema, registered model, and model serving endpoint names. Other special characters still normalize as before, and generated development prefixes retain their separator.Why
Issue #2305 reports that
${workspace.current_user.short_name}_joined with schemaqcproducesmy_userqcinstead ofmy_user_qc. A follow-up reports the same behavior for registered models and serving endpoints.Existing deployments: Correcting these effective names can change resource identities after a CLI upgrade, even when the bundle configuration has not changed. With the current direct engine, affected schemas rename in place and keep their
schema_id, but references to the old qualified name need updating. Registered models and serving endpoints still plan recreation when their names change. Existing users should inspectbundle planand plan updates to references and endpoint clients before deploying.The issue discussion flags compatibility concerns. Maintainers need to decide whether changing the default normalization is acceptable for a release or whether the correction should require an opt-in setting. This PR currently changes the default.
Fixes #2305
Tests
go test ./bundle/config/mutator/resourcemutator -run '^TestApplyPresets' -count=1go test ./acceptance -run '^TestAccept/bundle/presets/(name_prefix_underscores|name_prefix_existing_schema)$' -count=1: both local DMS variants. The existing-state fixture simulates an old effective schema name, confirms an in-place rename to the corrected name with the sameschema_id, and then checks for a clean plan../task checks(including changelog validation). The new YAML was formatted with the repository'syamlfmttool.Remote migration was not exercised.
This PR was written by Codex.